Configurable Streetlight Sensor Platform

ABSTRACT

The technology described in this document is embodied in a sensor platform that includes an enclosure for housing one or more sensors, the enclosure configured to be deployed between a streetlight and a streetlight controller that manages operations of the streetlight. The sensor platform also includes an electrical receptacle for receiving the streetlight controller in a substantially secure configuration. The sensor platform also includes an electrical connector for connecting the enclosure to the streetlight. The sensor platform also includes at least one pass-through connector disposed within the enclosure to provide an electrical connection between the electrical connector and the electrical receptacle.

PRIORITY CLAIM

This application is a continuation application of, and claims priorityto U.S. application Ser. No. 15/446,861, filed on Mar. 1, 2017 (to beissued as U.S. Pat. No. 10,094,546 on Oct. 9, 2018), which claimspriority to U.S. Provisional Application 62/338,769, filed on May 19,2016. The entire contents of both applications are incorporated hereinby reference.

TECHNICAL FIELD

This disclosure generally relates to a configurable platform for sensorslocated on streetlights.

BACKGROUND

Many cities and towns have thousands of streetlights to keep streets andwalkways lit at night. A given streetlight may be turned on or off usinga photocell deployed on the streetlight.

SUMMARY

In one aspect, this document features a sensor platform that includes anenclosure for housing one or more sensors, the enclosure configured tobe deployed between a streetlight and a streetlight controller thatmanages operations of the streetlight. The sensor platform also includesan electrical receptacle for receiving the streetlight controller in asubstantially secure configuration, and an electrical connector forconnecting the enclosure to the streetlight. The sensor platform alsoincludes at least one pass-through connector disposed within theenclosure to provide an electrical connection between the electricalconnector and the electrical receptacle.

In another aspect, this document features an apparatus that includes astreetlight controller that manages operations of a streetlight, and asensor platform. The sensor platform includes an enclosure for housingone or more sensors, the enclosure configured to be deployed on thestreetlight, an electrical receptacle for receiving the streetlightcontroller in a substantially secure configuration, an electrical plugfor connecting the enclosure to the streetlight, and one or morepass-through connectors disposed within the enclosure to provide anelectrical connection between the electrical plug and the electricalreceptacle.

In another aspect, this document features a streetlight that includes astreetlight housing including a lamp, a streetlight controller thatmanages one or more operations of the streetlight, and a sensor platformdisposed between the streetlight controller and the streetlight housing.The sensor platform includes one or more sensors, an electricalreceptacle for receiving the streetlight controller in a substantiallysecure configuration, an electrical plug for connecting the sensorplatform to the streetlight housing, and one or more pass-throughconnectors disposed between the electrical plug and the electricalreceptacle for providing an electrical connection between thestreetlight housing and the streetlight controller.

Implementations of the above aspects can include one or more of thefollowing.

The one or more sensors can include at least one of an environmentalsensor, a noise sensor, a seismic sensor, a threat sensor, a contactsensor, and a motion sensor, a parking sensor, a pedestrian counter, anda traffic counter. At least a subset of the one or more sensors can be apart of a wireless sensor network. The wireless sensor network caninclude one or more external sensors disposed outside the enclosure ofthe sensor platform.

The sensor platform can also include a circuit board disposed within theenclosure, wherein the circuit board includes a plurality of slotsconfigured to receive at least a subset of the one or more sensors. Atleast some slots in the plurality of slots can be electrically connectedto the pass-through connector. At least some slots in the plurality ofslots can be electrically connected to an input/output line of one ormore processors, for example, to sample, process, store, and communicatethe data being sensed by the one or more sensors. One or more of theslots can be connected to the pass-through connector through analternating current (AC) to direct current (DC) converter. One or moreof the slots can include an input/output port electrically connected toan input/output line of one or more processors. The electricalreceptacle of the sensor platform can comply with a standard associatedwith streetlight fixtures. The standard can be set by NationalElectrical Manufacturers Association (NEMA). Power for the one or moresensors can be provided through the pass-through connector. The sensorplatform can include an outlet configured to provide power to anexternal sensor or device, wherein the outlet is connected to the atleast one pass through connector.

In some implementations, the technology described herein may have one ormore of the following advantages. A configurable sensor platform (whichmay be co-located with a streetlight controller) on a streetlight mayallow for multiple sensors to be implemented on the streetlight whiletaking advantage of existing communications connections and powersources. Such a configurable sensor platform may also increasecapability for monitoring and reporting conditions on or around thestreetlight. For example, the sensor platform can be configured toinclude sensors for monitoring a threat (e.g. a biohazard, or agunshot), an environmental condition (e.g. carbon monoxide levels),weather, or traffic conditions. In some implementations, the sensorplatform can be configured to detect the presence of wireless devicesnear the streetlight, such that location-specific information may bedelivered to the wireless devices.

In some cases, the sensor platform may be customized with differenttypes of sensors. This customizability may allow developers or users todesign or select sensors for inclusion in the configurable sensorplatform, based on their particular requirements. The configurablesensor platform may be configured to be moved from one streetlight toanother as needed. Such portability may be useful, for example, to movea set of sensor platforms to a particular area of interest in a city orin an area surrounding a special event.

In some cases, the configurable sensor platform may also allow forimproved streetlight control by providing one or more inputs to astreetlight controller. Such inputs may be used by the streetlightcontroller in deciding, for example, a mode of operation for thestreetlight. For example, the inputs can be used by the controller todetermine whether to switch the streetlight on or off, or to operate thestreetlight at a predetermined level of dimness. For example,streetlights can be set to a predetermined level of dimness in one modeof operation to save energy. If a sensor disposed in the sensor platformdetects motion near the streetlight, the platform may provide theinformation to a streetlight controller such that the streetlightcontroller turns the streetlight on to full power for a predeterminedamount of time.

Two or more of the features described in this disclosure, includingthose described in this summary section, may be combined to formimplementations not specifically described herein.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features,objects, and advantages will be apparent from the description anddrawings, and from the claims.

DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example of a streetlight management system.

FIG. 2A is a top view of an example of a sensor platform housing.

FIG. 2B is a side view of the sensor platform housing of FIG. 2A.

FIG. 2C is a bottom view of the sensor platform housing of FIG. 2A.

FIG. 3A is a circuit diagram showing the interfaces and internalcomponents of an example of a sensor platform.

FIG. 3B is a block diagram showing the interfaces and internalcomponents of an example of a sensor module of a sensor platform.

FIG. 4 is a block diagram showing an example of a computing device.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

Streetlight controllers disposed on streetlights may be used forcontrolling the streetlights in various ways. In some implementations,the streetlight controllers can be programmed to turn on, turn off, ordim the streetlight, for example, at scheduled times, or based on a setof conditions. The streetlight controllers can also be used inconjunction with photocells, for example, to make lighting decisionsbased on ambient weather conditions. Streetlight controllers may includeone or more sensors that can be used to make decisions regarding theoperational mode of the corresponding streetlights. For example, astreetlight controller can include a light sensor such as a photocell todetermine whether the ambience is dark enough to warrant switching thestreetlight on. In fact, due to the location and ubiquity ofstreetlights, in some cases, it may be advantageous to dispose varioustypes of sensors on the streetlights. Disposing such sensors onstreetlights may provide specific advantages. For example, disposing atraffic counter on a streetlight could allow a city to gather andanalyze traffic data to determine, for example, how to efficientlyallocate funding for road repairs. In another example, disposing anenvironmental sensor, like a pollutant sensor, on a streetlight couldallow for monitoring pollution, including, for example, a level ofcarbon dioxide or carbon monoxide, a concentration of particles in theair, etc. In another example, disposing a motion sensor on a streetlightcould increase energy efficiency by allowing the streetlight to beturned on upon sensing motion and turned off or dimmed after a setperiod of time in the absence of motion. In general, the sensors thatare deployed on a streetlight may be selected based on variousrequirements that may depend on, for example, events, location, time,and/or availability of new sensors.

Sensors can be deployed on streetlights in various ways. For example,the sensors may be directly incorporated into a streetlight controller.However, this would require custom-made streetlight controllers forvarious combinations of sensors. In addition, an existing controller mayhave to be replaced if a new sensor is desired to be deployed, which inturn may be inefficient and expensive. The sensors could alternativelybe independently deployed on the streetlight. However, such independentdeployment may require new connections, which may vary from one sensorto another.

The technology described in this document provides a configurable sensorplatform that allows for deployment of one or more sensors on thestreetlight while utilizing connections available on a streetlight. Theconfigurable sensor platform may include a sensor module, which may becustomized to include the user's desired sensors. For example, thesensor module can include multiple sensor receptacles configured toreceive various combinations of desired sensors. In someimplementations, the configurable sensor platform is customized suchthat the sensor platform may be connected to a standard receptacle on astreetlight. Thus, the sensor platform may facilitate use of power fromthe streetlight as a power source for the sensors. The streetlight powercan be used, for example, as a primary power source, a secondary orback-up power source, or a power source for charging a storage devicesuch as a battery that in turn powers one or more sensors on the sensorplatform. In some implementations, the configurable sensor platform mayinclude a landing area configured to facilitate operations of unmannedaerial vehicles (UAVs) such as drones. For example, such a landing areacan be configured to allow UAVs to take-off, land, or park on the sensorplatform. In some implementations, the sensor platform can include oneor more sensors for monitoring/metering activities of the UAVs using thelanding area, and/or a power outlet for charging the UAVs parked on thelanding area. For example, in some implementations, a sensor platformmay include a charging port configured to allow an UAV to connect to apower source. The power supply to the streetlight could be used as thepower source for the charging of the UAV.

Referring to FIG. 1, an example of a streetlight system 100 can includemultiple streetlights 102 which may be electrically connected withsensor platforms 126 and/or streetlight controllers 104. The sensorplatform 126 can be configured to communicate with other sensorplatforms deployed on streetlights 102 within a network 106. Network 106can include a network of streetlight controllers 104 and/or a network ofsensor platforms 126. In some implementations, the sensors on the sensorplatform 126 can communicate via transceivers on the streetlightcontroller 104.

In some implementations, the network 106 can be configured tocommunicate with a remote server 116, for example, over a communicationnetwork 110. In some implementations, the network 110 can communicatewith the server 116 via one or more gateways or access points 108. Insome implementations, the network 110 can communicate with the server116 directly. In some implementations, the server 116 can include anindustrial control system. In some implementations, the server 116 canbe a supervisory control and data acquisition (SCADA) server. In someimplementations, the server can be a central management server. In someimplementations, the server 116 can be a server farm that includesmultiple servers.

The network 110 can include one or more gateways 108. The gateways 108can be data coordinator units that act as a link between the streetlightcontrollers 104 and sensor platforms 126 and the server 116. A gateway108 can be configured to communicate with multiple streetlightcontrollers 104 and/or sensor platforms 126. For example, a gateway 108can be configured to support up to 1000 streetlight controllers 104and/or sensor platforms 126. In some implementations, the gateway 108can communicate with other gateways 108 through a wired or wirelessconnection. In some implementations, the gateways 108 can communicatewith the server 116 through a wired connection (e.g., Ethernet). In someimplementations, the gateways 108 can wirelessly communicate with theserver 116. In some implementations, gateways 108 can use Global Systemfor Mobile Communications (GSM) or General Packet Radio Service (GPRS)to wirelessly communicate with the server 116. A firewall 114 canseparate the gateways 108 and the server 116 to keep the server 116secure.

The gateway 108 can be a computing device mounted on an existingstructure such as a streetlight, electric pole, or building. The gateway108 can include, for example, one or more of a processor, a real-timeclock, a transceiver, a memory, an Ethernet port, a USB port, and aserial port. The gateway 108 can connect to a computing device such asthe server 116 using one of its ports. The gateway 108 can have anenclosure for wall mounting or an enclosure for pole mounting. Theenclosure can be made from polycarbonate.

In some implementations, the network 110 and the server 116 can beseparated by a security layer such as a firewall 114. In someimplementations, the network 110 can include a computing device (e.g. amedia convergence server (MCS)) that receives information from variousgateways 108 and communicates with the server 116, for example, using anEthernet connection. Such a computing device can also be configured torelay information received from the server 116 to the gateways 108. Insome implementations, the gateways 108 can be configured to communicatedirectly with the server 116.

In some implementations, the server 116 can be configured to communicatewith various computing devices related to managing the streetlights 102.One or more of these devices can be configured to execute an applicationthat facilitates individual or grouped management of the streetlights102. For example, the server 116 can be configured to communicate withfield staff using, for example, mobile devices 120 and office staffthrough computing devices 122. In some implementations, the server 116can communicate with one or more computing devices that execute astreetlight management software. In some implementations, the server 116executes the streetlight management software and providesuser-interfaces on one or more of the mobile device 120 and thecomputing device 122.

In some implementations, the sensor platform 126 can be configured tointerface with a streetlight controller 104 deployed on a streetlight102. For example, the sensor platform 126 may be deployed between astreetlight 102 and a streetlight controller 104 such that the sensorplatform 126 is powered from connections available on the streetlight102, and maintains a functional connection between the streetlight 102and the streetlight controller 104. In some implementations, the sensorplatform 126 may also be configured to maintain a functional connectionbetween a streetlight 102 and a photocell associated with thestreetlight 102. This functional connection may be maintained such thatpower from the streetlight is passed through the sensor platform 126 tothe associated streetlight controller 104 or photocell.

In some implementations, the sensor platform 126 can be mounted on astreetlight. The sensor platform 126 can be placed within an enclosurethat is mounted on a streetlight 102. The enclosure can have anelectrical connector 206 (e.g. a two, three, or four pronged plug, or amulti-pin connector such as a five or seven-pin connector) that can beconnected to an electrical receptacle on a streetlight 102. This isillustrated in the examples of FIG. 2B and FIG. 2C, which show theconnections on a sensor platform 126 that allow the sensor platform 126to electrically interface with a streetlight 102, a streetlightcontroller 104, or a photocell.

Referring to FIG. 2A, a sensor platform 126 includes an enclosure 202and an electrical receptacle 204. In some implementations, the sensorplatform 126 can receive an electrical connector of a streetlightcontroller 104 or a photocell via the electrical receptacle 204. Theelectrical connector and the corresponding receptacle can be inaccordance with the standards used in the country in which thestreetlight is deployed. For example, in the United States, theelectrical connector and the corresponding receptacle can be inaccordance with standards set by National Electrical ManufacturersAssociation (NEMA). This electrical connection between the electricalreceptacle 204 of the sensor platform 126 and an electrical connector ofa streetlight controller 104 or a photocell allows power to be relayedfrom a streetlight 102 through the sensor platform 126 via a passthrough connector (shown in FIG. 3A) to the streetlight controller 104or photocell.

Referring to FIG. 2B, the sensor platform 126 can have an electricalconnector 206 that can be connected to an electrical receptacle on astreetlight 102 (see FIG. 1). The electrical connector 206 and thecorresponding receptacle on the streetlight 102 can be in accordancewith the standards used in the country in which the streetlight isdeployed. In some implementations, the electrical connector 206 can be atwist-locking plug. The electrical connector 206 and the correspondingreceptacle can be in accordance with the standards used in the countryin which the streetlight is deployed. For example, in the United States,the electrical connector and the corresponding receptacle can be inaccordance with standards set by National Electrical ManufacturersAssociation (NEMA).

In some implementations, the enclosure 202 can be attached to thestreetlight housing using other forms of connectors such as a threadedconnector that can be twisted or screwed into an appropriately threadedreceptacle disposed on the streetlight. The threaded receptacle capableof receiving the threaded connector of the enclosure 202 can be, forexample, an integral part of the streetlight housing, or affixed to thestreetlight housing. The sensor platform 126 can therefore beelectrically connected to a power source on the streetlight 102 via aconnection disposed on the streetlight. Therefore, the technologydescribed herein provides a configurable sensor platform 126 that iscapable of receiving various sensors, and reduces or potentiallyobviates the need for additional wiring by using existing connections onthe streetlight. The streetlight 102 may provide AC or DC power to theelectrical connector 206. In some implementations, the sensor platform126 can be attached to the streetlight housing using a threadedconnector that can be twisted or screwed into an appropriately threadedreceptacle disposed on the streetlight 102. The threaded receptaclecapable of receiving the threaded connector of the streetlightcontroller housing can be, for example, an integral part of thestreetlight housing, or affixed to the streetlight housing.

In some implementations, the sensor platform 126 may be used with astreetlight controller 104 or a photocell (not shown). The sensorplatform 126 can have an electrical receptacle 204 for receiving anelectrical connector of a streetlight controller 104 or a photocell, asdiscussed in the description of FIG. 2A. In some implementations, theconnector and the corresponding receptacle can be in accordance with thestandards used in the country in which the streetlight is deployed. Forexample, in the United States, the connector can be a twist-locking plugin accordance with standards set by NEMA.

Referring to FIG. 2C, the sensor platform 126 may have an electricalconnector 206. In the depicted embodiment, the electrical connector 206is a NEMA 7-pin connector (compatible with an ANSI C136.41 DimmingReceptacle). Three central pins 210 may be used to relay power forpowering both the sensor platform 126 and an associated streetlightcontroller 104 or photocell. Two of the outside pins 208, may be usedfor dimming the streetlight. The remaining outside pins 208 can beavailable to capture and communicate additional sensor data. Thisadditional sensor data may originate from sensors included in the sensorplatform 126, or from sensors included in a streetlight controller 104.The central pins 210 and outside pins 208 shown in this embodiment makeup an electrical connector 206 that is a standard NEMA ANSI C136.41Dimming Receptacle 7-pin connector. The sensor platform 126 can bemounted on a streetlight 102 in various configurations.

In some implementations, a streetlight controller 104 can be mounted ona sensor platform 126, which in turn can be mounted on a streetlight 102as shown in the inset 130 of FIG. 1. In some implementations, the sensorplatform may be mounted on a streetlight controller. In someimplementations, the sensor platform may be integrated within thestreetlight controller. In some implementations where the sensorplatform is integrated within the streetlight controller, the sensorplatform is integrated in a removable configuration. In someimplementations where the sensor platform is mounted on a streetlightcontroller, the sensor platform may include a solar cell configured topower one or more sensors of the sensor platform. The streetlightcontroller housing can have an electrical connector 206 (e.g. a two,three, or four-pronged plug, or a multi-pin connector such as a five orseven-pin connector) that can be connected to an electrical receptacle204 on a sensor platform 126. In some implementations, the sensorplatform 126 includes a pass-through connector that is coupled betweenan electrical connector 206 (such as a connector compatible with an ANSIC136.41 Dimming Receptacle) and an electrical receptacle 204 (such as aNEMA ANSI C136.41 Dimming Receptacle). This is described below inadditional detail with reference to FIG. 3A. The pass through connectorallows power to be pulled from the streetlight 102, through the sensorplatform 126, and delivered to the streetlight controller 104. In thisway, the additional sensors can be deployed without disruptingfunctional connectivity between the streetlight 102 and streetlightcontroller 104.

In some implementations, the sensor platform 126 may be configured toreceive a photocell via a corresponding electrical receptacle 204. Insome implementations, the photocell can be mounted as a part of ahousing of the streetlight controller 104. In some implementations, thephotocell can be a separate unit having a connector for connecting to areceptacle 204 on the sensor platform 126 or to a receptacle on thestreetlight controller 104. The photocell can detect ambient light, andthe streetlight controller 104 can receive light measurement data fromthe photocell. In some implementations, the light measurement data canbe used to make lighting decisions or override an active lightingschedule (e.g., on/off/dim settings as per a pre-set schedule). In someimplementations, the connector 206 and the corresponding receptacle canbe in accordance with the standards used in the country in which thestreetlight 102 is deployed. For example, in the United States, theconnector 206 can be a twist-locking plug in accordance with standardsset by NEMA.

A sensor platform 126 may be disposed on a streetlight 102 toincorporate various sensors into the network 106, which in turn mayenhance the ability of the network 106 to gather information onconditions at or near the streetlight 102. The information gatheredwould depend on the particular sensors deployed in the sensor platform126 and installed external to the sensor platform and may include, forexample, pollution conditions, traffic conditions, pedestrian trafficinformation, safety conditions, or other environmental conditions. Thesensors may be disposed, for example, in a sensor module of theconfigurable sensor platform 126. The individual sensors included in thesensor platform 126 may be selected by an authority or user in charge ofthe deployment. For example, the sensors on sensor platforms 126 to bedeployed in a particular city may be selected by the correspondingmunicipality, based on the conditions desired to be monitored. Thesensors that may be deployed in the sensor platform 126 can include, forexample, environmental sensors, carbon monoxide sensors, carbon dioxidesensors, noise sensors, seismic sensors, threat sensors, radioactivitysensors, biochemical sensors, contact sensors, motion sensors, parkingsensors, traffic counters, or pedestrian counters. Types of sensors thatmay be included in the sensor platform include, for example, acousticsensors such as microphones, vibration sensors such as seismographs,automotive sensors, chemical sensors such as carbon monoxide or carbondioxide detectors, electrical sensors such as ammeters and voltmeters,magnetic sensors, wireless sensors, flow sensors, fluid velocitysensors, sensors configured to measure position/speed/acceleration ofpassing vehicles, optical/imaging sensors such as cameras ornumber-plate readers, pressure sensors such as barometers, forcesensors, density and/or level sensors, thermal sensors,proximity/presence sensors such as motion detectors, environmentalsensors, wind-speed sensors, hygrometers, and radio frequencyidentification (RFID) detectors. In some implementations, one or moresensors may be deployed on the streetlight, but not on the sensorplatform. In such cases, the sensors external to the sensor platform canbe configured to communicate with the sensor platform over wired orwireless connections.

Different combinations of sensors may be deployed in a sensor platform126 based on particular concerns in certain areas. For example, threatsensors, like biochemical sensors or radioactivity sensors, may beincluded in sensor platforms 126 to be deployed on streetlights 102close to an airport, a stadium, or a large public gathering space. Insuch cases, the sensors could gather safety information to be relayed topolice or other public safety officials. In another example, trafficsensors may be included in sensor platforms 126 to be deployed onstreetlights 102 close to busy roads or high traffic areas. As otherexamples, motion sensors and parking sensors may be included in sensorplatforms 126 to be deployed on streetlights 102 in parking lots, andnoise sensors may be included in sensor platforms 126 to be deployed onstreetlights 102 in residential areas. In some implementations, thesensor platform 126 may also be portable such that the sensor platform126 can be removed from one streetlight 102 and installed on another asdesired. This may be advantageous when data gathered from the sensorswould be useful in a particular area of a city at a particular time, forexample, for a special event. In one particular example, if a city ofmunicipality owns a limited number of sensor platforms 126 (e.g.,platforms including traffic and parking sensors), the platforms can bedeployed on compatible streetlights at one location for a particularevent, and then moved to compatible streetlights at a different locationfor another event. Because the sensor platforms 126 can be deployed withor without addition streetlight equipment (e.g., streetlight controller104 or photocell), the portability is independent of whether or not thecompatible streetlights include such equipment.

In some implementations, information gathered by the sensors of thesensor platform 126 may be sent to the streetlight controller 104 whichthen decides which mode to place the streetlight in, either on, off, orat a particular level of dimness. A configurable sensor platform mayalso allow for controlling other devices that may be located at or nearthe streetlight. For example, the sensor platform 126 can be configuredto communicate with an external camera, and may direct the camera topoint in a certain direction or to start or stop recording based on oneor more control signals received from the sensor platform 126. Such acontrol signal can be generated based on the output of one or moresensors disposed on the sensor platform 126. Information gathered by thesensors of the co-located sensor platform 126 may also be communicatedover the network 106 and analyzed at an external computing device orserver, for example, by police, government, or another party. In someimplementations, the sensor platform 126 may communicate informationover the network 106 utilizing a communication module of an associatedstreetlight controller 104.

In some implementations, information gathered by the sensors of thesensor platform 126 may be used to communicate information to users inclose proximity to the streetlight 102. The sensor platform 126 can beconfigured to communicate with a mobile device 128 that is in closeproximity to the sensor platform 126. For example, the sensor platform126 may request and then receive location data from mobile device 128.The sensor platform 126 may then push relevant data to the mobiledevice, such as location-based news or alerts, including, for example,nearby events, safety alerts, or coupons for nearby businesses. Forexample, a sensor platform 126 deployed on a streetlight 102 close to ashopping center may receive a signal (e.g., a signal indicative oflocation data) from a mobile device 128 indicating that the mobiledevice 128 is in close proximity to the streetlight 102. Upon receivingthe signal from the mobile device 128, the sensor platform 126 may sendcoupons, operating hours, or special event information related to theshopping center to the mobile device 128. In an additional example, asensor platform 126 deployed on a streetlight 102 in a parking lot mayreceive location data from a mobile device 128 indicating that themobile device 128 is in close proximity to the streetlight 102. Uponreceiving this location data from the mobile device 128, the sensorplatform 126 may send parking information, such as hourly rates orparking reminders, such as the specific section parked in to the mobiledevice 128.

In some implementations, the sensor platform 126 can be configured tocommunicate with a motor vehicle. In some implementations, the sensorplatform can be configured to communicate with a mobile device 128connected to a motor vehicle. The data pushed to the motor vehicle mayinclude traffic information, roadwork information, safety information,news, coupons, or advertisements. This data could be pushed to a displayor speakers in the motor vehicle.

The sensor platform 126 can be configured to communicate with otherstreetlight controllers and/or sensor platforms, as well as gateways108, or external sensors located on, or in the vicinity of thestreetlight 102. For example, a sensor platform 126 may communicate withother streetlight controllers 104, sensor platforms 126, or externalsensors through a wired or wireless connection. The sensor platform 126can include a transceiver to wirelessly communicate with otherstreetlight controllers 104, sensor platforms 126, external sensors, orgateways 108. The transceiver can use a radio frequency (RF) portion ofthe spectrum for the communications. The sensor platforms 126 within thenetwork 106 can be connected to one another by a wired or wirelessnetwork. For example, the sensor platforms 126 can be connected to oneanother by a mesh network. A sensor platform 126 can act as a node ofthe mesh network, and/or serve as a relay for other nodes to propagatedata using the mesh network. The mesh network can be self-forming and/orself-healing. Information from the sensors included in the sensorplatform 126 and information from external sensors may be transmitted toa provided communications network 110. The communications network 110may then communicate this sensor data to a central management system.This central management system may further process the sensor data. Insome implementations, the central management system may make decisionsregarding changing an operating mode of one or more streetlights 102 innetwork 106, informing an authority of the existence of a particularevent or condition at or in the vicinity of a streetlight 102. Thisevent or condition may be, for example, an environmental or threatcondition, a gunshot, a traffic event, a movement, or a weathercondition.

FIG. 3A shows a block diagram of an example implementation of the sensorplatform. As shown in FIG. 3A, the sensor platform 126 can include apass through connector 306 for powering included sensors and for passingpower to an associated photocell or streetlight controller 104. Powerfrom a streetlight 102 is delivered to the sensor platform's NEMA ANSIC136.41 Dimming Receptacle plug 326 which electrically connects to anelectrical receptacle on the streetlight 102. A NEMA plug 326 is anexample of an electrical connector 206. In some implementations, anotherconnector may replace the NEMA ANSI C136.41 Dimming Receptacle plug 326.This power may be AC or DC power. Power then is passed through thesensor platform 126 via lines 302 and 304, which make up pass throughconnector 306 to the sensor platform's NEMA receptacle 328. In someimplementations, the pass through connector 306 can be connected to oneor more additional receptacles (e.g., power outlets) located on thesensor platform. Examples of such additional receptacles include an ACoutlet, a universal serial bus (USB) port, or a Power over Ethernet(PoE) port. In some implementations, such a receptacle can be connecteddirectly to the pass through connector 306 to provide AC power to adevice connected via the receptacle. In some implementations, such areceptacle may be connected to the pass through connector 306 via an ACto DC converter (e.g., a switched-mode power supply) to provide DC power(e.g., 5V, 12V, or 3.3V DC) to a device connected via the receptacle.External sensors or other external devices may be connected to andpowered through such one or more additional receptacles. For example, acharging port for an UAV may be powered through the pass throughconnector 306.

A NEMA receptacle 328 is an example of an electrical receptacle 204. Insome implementations, another connector may replace the NEMA plug 326.In some implementations, the lines 302 and 304 split to provide power toone or more processors 320, radio module 318, and sensor module 322, inaddition to delivering power to the sensor platform's NEMA receptacle328. A switched-mode power supply 316 efficiently transfers power to theprocessor 320, radio module 318, and sensor module 322. A surgeprotection module 314 protects the processor 320, radio module 318, andsensor module 322. A photocell or streetlight controller 104 or shortingcap can be plugged into the sensor platform's NEMA receptacle 328 toutilize the power passed from the streetlight to the NEMA receptacle 328to control the operation of the streetlight. A sensor platform 126 mayalso include two lines capable of sending information for dimming thestreetlight from a streetlight controller 104 connected to the sensorplatform's NEMA receptacle 328, DIM+ 310 to brighten the streetlight andDIM− 312 to dim the streetlight.

Referring to FIG. 3B, in some implementations, the sensor platform 126can be made configurable, allowing different combinations of individualsensors to be included in the sensor module 322 of the sensor platform126. In some implementations, the sensor module 322 may include aplurality of slots 330 to which individual sensors 332 may be connected.The slots 330 can be connected to other modules of the sensor platform126 such that sensors received within a slot can readily use the othermodules. For example, each slot 330 can be connected to the switchedmode power supply (SMPS) 316 through electrical connection 334, makingpower available to a sensor 332 connected to the slot 330. In anotherexample, each slot 330 can be connected to a processor 320 through aconnection between an input/output port of the slot and the input/outputlines 324. The connections between input/output ports of the slots andthe input/output lines 324 may be used, for example, to communicate databetween the two or more sensors 332 and/or between the sensors 332 andthe processor 320. In some implementations, the input/output lines 324may also provide a connection between the slots 330 and a radio module318 of the sensor platform. The one or more processors 320 of the sensorplatform 126 may send data to, and/or receive data from one or more ofthe radio module 318 and the sensor module 322 through the input/outputlines 324.

In some implementations, the slots 330 allow the sensor platform 126 tobe configured with a customized set of sensors. For example, the sensorplatform 126 can be made available to developers, allowing them toconfigure the sensor module 322 to include appropriate combinations ofsensors as needed. As described above, the sensors that can be includedon the sensor module include, for example, various combinations of oneor more environmental sensors, carbon monoxide sensors, carbon dioxidesensors, noise sensors, seismic sensors, threat sensors, radioactivitysensors, biochemical sensors, contact sensors, motion sensors, parkingsensors, traffic counters, or pedestrian counters. In someimplementations, the sensor module 322 can be made configurable byincluding a circuit board having multiple slots for receiving individualsensors. The individual sensors may be connected, for example, toinput/output lines 324 by input/output ports. Input/output lines 324 maybe used for sending and receiving information between the processor andthe sensors.

In some implementations, the radio module 318 can include circuitry(e.g., one or more transceivers) configured to wirelessly communicateusing one or more communication technologies. The communicationtechnologies can include, for example, Wi-Fi, Bluetooth®, ZigBee,iBeacons, near-field communications (NFC), cellular, or otherproprietary or non-proprietary technologies. The radio module 318 mayallow the sensor platform 126 to communicate with an associatedstreetlight controller 104, with other sensor platforms 126 located onother streetlights in the streetlight network 106 (shown in FIG. 1), orto a gateway 108 on a network 110 (shown in FIG. 1). The radio module318 also may allow the sensor platform 126 to communicate with a mobiledevice 128 in close proximity to the streetlight 102 upon which thesensor platform 126 is deployed.

The radio module 318 may also allow the sensor platform 126 towirelessly communicate with, and/or control, external sensors or deviceslocated on or near the streetlight. In some implementations, the sensorplatform 126 may also communicate with external sensors or deviceslocated on the streetlight via a wired connection. Communication withthese external sensors or devices may allow the sensor platform 126 oran associated streetlight controller 104, for example, to controloperations of the external sensors or devices, or to control thestreetlight 102 to operate in a particular mode. In one example, where asensor platform 126 includes a traffic sensor, the sensor platform 126may generate a control signal to operate a camera disposed on thestreetlight responsive to determining a traffic condition such as atraffic back-up. The control signal can be configured to, for example,direct the camera to capture the event and provide a video/image feed toa traffic information server. In another example, where the sensorplatform 126 includes a gunshot sensor, the sensor platform 126 cantransmit, upon receiving information indicative of detection of agunshot, an alert signal that is transmitted to law enforcementauthorities. The sensor platform 126 may also generate a control signalfor a camera disposed on the streetlight to record in the direction fromwhich the gunshot originated.

In another example, the sensor platform 126 may include a weathersensor. Upon receiving an indication from the weather sensor thatsnowfall is occurring, the sensor platform 126 may direct an externalsensor to measure the snow accumulation or may direct a camera to take aphoto of the snow accumulation in a particular area where a measuringstick is located. In some implementations, information from one or moreexternal sensors may also be routed through the sensor platform 126. Forexample, information received from the one or more external sensors maybe communicated by the sensor platform 126 to an associated streetlightcontroller 104, for example, to direct the streetlight 102 to operate ina particular mode. The sensor platform 126 could also communicate withother sensor platforms 126 or streetlight controllers 104 in the network106 to direct all streetlights in a group to operate in a particularmode. For example, an external weather sensor may indicate to a sensorplatform 126 that it is snowing or raining. With this information fromthe external weather sensor, the sensor platform 126 may communicate theweather status to other sensor platforms 126 or streetlight controllers104 connected over the network 106 to turn all streetlights 102 (orstreetlights within a predetermined vicinity of the weather sensor) tofull power. In another example, based on information indicative ofmotion detected by an external motion sensor, the sensor platform 126may communicate with other sensor platforms 126 or streetlightcontrollers 104 connected over the network 106 to turn streetlights 102in a particular area (e.g. in a parking lot or along a particular blockof a street) to full power. In some implementations, the sensor platform126 can be connected to an external sensor configured to detect a breachof security at the streetlight itself. For example, a streetlight boxenclosing connections at the base of the streetlight can be equippedwith a sensor (e.g., a magnetic or electric sensor) configured to detecta breach of the streetlight box. Upon receiving indication of a breach(e.g., an attempted wire theft) from such an external sensor, the sensorplatform can be configured to perform one or more remedial/preventiveactions such as sending an alert to appropriate authorities, triggeringa camera to capture images/video of the vicinity of the streetlight,and/or sound an alarm to deter the perpetrators of the breach.

In some implementations, the sensor platform may communicate withsensors in the vicinity of the streetlight pole, but not directly on thepole. In some implementations, the sensor platform may communicate witha sensor on a nearby trash can. A sensor on a trash can could indicatethat the can is full, or a certain percentage full. This level sensorcould inform when the trash can should be emptied, for example byalerting a municipal worker.

FIG. 4 shows an example of a computing device 400 and a mobile device450, which may be used with the techniques described here. For example,referring to FIG. 1, the gateway device 108, streetlight controller 104,or devices 116, 120 or 122 could be examples of the computing device 400or the mobile device 450. In some implementations, at least portions ofthe computing device 400 or the mobile device 450 can be used forimplementing the radio module 318 and/or the sensor module 322.Computing device 400 is intended to represent various forms of digitalcomputers, such as laptops, desktops, workstations, personal digitalassistants, servers, tablet computers, blade servers, mainframes, andother appropriate computers. Computing device 450 is intended torepresent various forms of mobile devices, such as personal digitalassistants, cellular telephones, smartphones, and other similarcomputing devices. The components shown here, their connections andrelationships, and their functions, are meant to be examples only, andare not meant to limit implementations of the techniques describedand/or claimed in this document.

Computing device 400 includes a processor 402, memory 404, a storagedevice 406, a high-speed interface 408 connecting to memory 404 andhigh-speed expansion ports 410, and a low speed interface 412 connectingto low speed bus 414 and storage device 406. Each of the components 402,404, 406, 408, 410, and 412, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 402 can process instructions for executionwithin the computing device 400, including instructions stored in thememory 404 or on the storage device 406 to display graphical informationfor a GUI on an external input/output device, such as display 416coupled to high speed interface 408. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices400 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 404 stores information within the computing device 400. Inone implementation, the memory 404 is a volatile memory unit or units.In another implementation, the memory 404 is a non-volatile memory unitor units. The memory 404 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 406 is capable of providing mass storage for thecomputing device 400. In one implementation, the storage device 406 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 404, the storage device 406,memory on processor 402, or a propagated signal.

The high speed controller 408 manages bandwidth-intensive operations forthe computing device 400, while the low speed controller 412 manageslower bandwidth-intensive operations. Such allocation of functions is anexample only. In one implementation, the high-speed controller 408 iscoupled to memory 404, display 416 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 410, which may acceptvarious expansion cards (not shown). In the implementation, low-speedcontroller 412 is coupled to storage device 406 and low-speed expansionport 414. The low-speed expansion port, which may include variouscommunication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet)may be coupled to one or more input/output devices, such as a keyboard,a pointing device, a scanner, or a networking device such as a switch orrouter, e.g., through a network adapter.

The computing device 400 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 420, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 424. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 422. Alternatively, components from computing device 400 may becombined with other components in a mobile device (not shown), such asdevice 450. Each of such devices may contain one or more of computingdevice 400, 450, and an entire system may be made up of multiplecomputing devices 400, 450 communicating with each other.

Computing device 450 includes a processor 452, memory 464, aninput/output device such as a display 44, a communication interface 466,and a transceiver 468, among other components. The device 450 may alsobe provided with a storage device, such as a microdrive or other device,to provide additional storage. Each of the components 450, 452, 464, 44,466, and 468, are interconnected using various buses, and several of thecomponents may be mounted on a common motherboard or in other manners asappropriate.

The processor 452 can execute instructions within the computing device450, including instructions stored in the memory 464. The processor maybe implemented as a chipset of chips that include separate and multipleanalog and digital processors. The processor may provide, for example,for coordination of the other components of the device 450, such ascontrol of user interfaces, applications run by device 450, and wirelesscommunication by device 450.

Processor 452 may communicate with a user through control interface 458and display interface 456 coupled to a display 44. The display 44 maybe, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display)or an OLED (Organic Light Emitting Diode) display, or other appropriatedisplay technology. The display interface 456 may comprise appropriatecircuitry for driving the display 44 to present graphical and otherinformation to a user. The control interface 458 may receive commandsfrom a user and convert them for submission to the processor 452. Inaddition, an external interface 462 may be provide in communication withprocessor 452, so as to enable near area communication of device 450with other devices. External interface 462 may provide, for example, forwired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 464 stores information within the computing device 450. Thememory 464 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 474 may also be provided andconnected to device 450 through expansion interface 472, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 474 may provide extra storage space fordevice 450, or may also store applications or other information fordevice 450. Specifically, expansion memory 474 may include instructionsto carry out or supplement the processes described above, and mayinclude secure information also. Thus, for example, expansion memory 474may be provide as a security module for device 450, and may beprogrammed with instructions that permit secure use of device 450. Inaddition, secure applications may be provided via the SIMM cards, alongwith additional information, such as placing identifying information onthe SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 464, expansionmemory 474, memory on processor 452, or a propagated signal that may bereceived, for example, over transceiver 468 or external interface 462.

Device 450 may communicate wirelessly through communication interface466, which may include digital signal processing circuitry wherenecessary. Communication interface 466 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 468. In addition, short-range communication may occur, suchas using a Bluetooth, Wi-Fi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 470 mayprovide additional navigation- and location-related wireless data todevice 450, which may be used as appropriate by applications running ondevice 450.

Device 450 may also communicate audibly using audio codec 460, which mayreceive spoken information from a user and convert it to usable digitalinformation. Audio codec 460 may likewise generate audible sound for auser, such as through a speaker, e.g., in a handset of device 450. Suchsound may include sound from voice telephone calls, may include recordedsound (e.g., voice messages, music files, and so forth) and may alsoinclude sound generated by applications operating on device 450.

The computing device 450 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 480. It may also be implemented as part of asmartphone 482, personal digital assistant, tablet computer, or othersimilar mobile device.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) or touchscreen by which the usercan provide input to the computer. Other kinds of devices can be used toprovide for interaction with a user as well. For example, feedbackprovided to the user can be any form of sensory feedback (e.g., visualfeedback, auditory feedback, or tactile feedback). Input from the usercan be received in any form, including acoustic, speech, or tactileinput.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), and theInternet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

Other implementations are also within the scope of the following claims.

1.-30. (canceled)
 31. A configurable sensor platform comprising: anenclosure configured to be deployed on a streetlight; a sensor modulecomprising a plurality of sensor receptacles configured to receive atleast a portion of various combinations of sensors the sensors beingselectable in accordance with a target functionality of the configurablesensor platform; at least one outlet configured to provide power to oneor more external sensors or devices located outside the enclosure; anelectrical connector for connecting the enclosure to a power source onthe streetlight; and at least one pass-through connector disposed withinthe enclosure to provide an electrical connection between the electricalconnector and the outlet.
 32. The configurable sensor platform of claim31, further comprising: a radio module for facilitating wirelesscommunication between the sensor platform and another wireless device;and one or more processing devices disposed in the enclosure, the one ormore processing devices configured to receive data from at least one ofthe plurality of sensors and send information to the radio module. 33.The configurable sensor platform of claim 31, wherein the outletcomprises a charging port for an unmanned aerial vehicle.
 34. Theconfigurable sensor platform of claim 31 wherein the at least one outletcomprises a receptacle configured to receive at least one of the one ormore external sensors or devices.
 35. The configurable sensor platformof claim 31, wherein the outlet is one of: an alternating current (AC)outlet, a direct current (DC) outlet, a universal serial bus (USB) port,or a Power-over-Ethernet (PoE) port.
 36. The configurable sensorplatform of claim 31, wherein the outlet comprises a receptacle inaccordance with standards set by National Electrical ManufacturersAssociation (NEMA).
 37. The configurable sensor platform of claim 31,wherein the electrical connector comprises a receptacle in accordancewith standards set by National Electrical Manufacturers Association(NEMA).
 38. The configurable sensor platform of claim 31, wherein theplurality of sensors comprises at least one of an environmental sensor,a noise sensor, a seismic sensor, a threat sensor, a contact sensor, ora motion sensor.
 39. The configurable sensor platform of claim 31,wherein the plurality of sensors comprise at least one of a parkingsensor, a pedestrian counter, or a traffic counter.
 40. The configurablesensor platform of claim 31, wherein at least a subset of the pluralityof sensors is a part of a wireless sensor network.
 41. The configurablesensor platform of claim 40, wherein the wireless sensor networkincludes one or more external sensors disposed outside the enclosure ofthe sensor platform.
 42. The configurable sensor platform of claim 31,wherein the sensor module comprises a circuit board and wherein thesensor receptacles comprise a plurality of slots on the circuit boardthe plurality of slots configured to receive at least a subset of theplurality of sensors.
 43. The configurable sensor platform of claim 42,wherein at least some slots in the plurality of slots are electricallyconnected to an input/output line of one or more processing devices. 44.The configurable sensor platform of claim 42, wherein one or more of theslots comprise an input/output port electrically connected to aninput/output line of one or more processors.